[FLINK-6025] [core] Add Flink's own JavaSerializer for Kryo serialization #3517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a reimplemented
JavaSerializer
to be registered withKryo. This is due to a know issue with Kryo's
JavaSerializer
that mayuse the wrong classloader for deserialzation (see EsotericSoftware/kryo#483).
Since we by default register Kryo's
JavaSerializer
forThrowable
s, users who need to serialize exception types as messages bump intoClassNotFoundException
s.Instead of registering Kryo's
JavaSerializer
forThrowables
, it is now changed to register the reimplementedJavaSerializer
.Generally, users who bump into
ClassNotFoundException
s if they are using Kryo'sJavaSerializer
fortheir own custom types are also recommended to change to Flink's
JavaSerializer
.The change is tested using the minimal issue reproducing example provided by our users in http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/AWS-exception-serialization-problem-td12063.html.